Print
1. Release History
November 12, 2007
Migration Wizard v.1.5.1 rev. 071102 for Sitecore CMS V5.3.1 is released
Sitecore versions: tested with Sitecore CMS V5.3.1 rev. 070924.
- Fixed: Load Content Snap-Shot button opened files from a hard-coded folder (Website Root\sitecore modules\migrate\backup\autosave).
- Fixed: Media files were not being transferred if the Media.FileFolder setting in web.config file of the target installation pointed outside the Sitecore root folder and uploadAsBlob was set to false in the migrationmodule.config file.
- Fixed: When a media item was transferred for the second time after it was deleted from the target it appeared with empty Extension, Height and Width fields.
- Fixed: Security was not transferred if custom domains were used.
- Fixed: Transferring of -1 item(s) completed was in the Transferring Results after the item without a template was transferred.
- Fixed: Items with '/' in the name were not transferred.
- Fixed: If Allows to store each backup in separate file setting was turned on the backup files were without an extension.
- Fixed: When force-major accident occurred (e.g. aspnet_wp.exe process had been restarted for some reason - PC restart, IIS reset, etc) Backup.xml and Report.xml were broken.
- Fixed: If the version of the item had blank values in the html/text fields the values from the latest non empty version were transferred.
- Fixed: When force-major accident occurred (e.g. aspnet_wp.exe process had been restarted for some reason - PC restart, IIS reset, etc) a tree loaded from a backup point was corrupted.
- Fixed: Items with '+' sign in name were transferred incorrectly.
- New Feature: Smart transferring engine has been added
- New Feature: The transferring option (inherit\allow\deny) changes after a user clicks on the tree node in the Migration Wizard
Data Migration Service v.1.5.1 rev. 071102 for Sitecore CMS V5.3.1 is released.
Sitecore versions: tested with Sitecore CMS V5.3.1 rev. 070924.
Data Migration Service v.1.0.5 rev. 071030 for Sitecore CMS V4 is released.
Sitecore versions: tested with Sitecore CMS V4.3.2.13. Expected to work with Sitecore CMS V4.3.2.x.
- Fixed: IndexAttribute field was transfered with an empty value from SC4.
- New Feature: Sitecore Client roles assigning when possible. If the Developer checkbox is checked for a user in the Sitecore CMS V4 this user will have the Sitecore Client Developing role in Sitecore CMS V5.3. The Sitecore Client Publishing role will be assigned to a user in Sitecore CMS V5.3 if the user has the Can Publish checkbox checked
June 22, 2007
Data Migration Service v.1.0.5 is released.
Sitecore versions: tested with Sitecore CMS v4.3.2.13. Expected to work with Sitecore CMS v4.3.2.x.
- Fixed: Problem with performance.
June 20, 2007
Data Migration Wizard v.1.5.0 is released.
Sitecore versions: tested with Sitecore CMS v5.3.1 rev.070515.
- Fixed: Versioned files stored on disk are not migrated correctly and are not inserted as blobs.
- New Feature: Save\Load tree selection is implemented.
- New Feature: Autosave tree selection is implemented.
- New Feature: Context menu is added to the migration tree.
- New Feature: Now it is possible to overwrite the default collision behavior for individual transferred items.
Data Migration Service v.1.5.0 is released.
Sitecore versions: tested with Sitecore CMS v5.3.1 rev.070515.
- New Feature: Transfer blob values option is implemented. It allows the blob values to be skipped.
May 25, 2007
Data Migration Wizard v.1.4.4 is released.
Sitecore versions: tested with Sitecore CMS v5.3.1 rev. 070515.
- Fixed: Create a link that has spaces in the path and bind it to an image in SC4 installation. Migrate to SC53 with all necessary handlers. Link isn’t updated in SC53.
- Fixed: Image transferring problem if the port is not set to 80.
- Fixed: All Editors should have write right to the language items.
- Fixed: ProcessMediaForFolders=|/upload/tratata/| doesn't work properly. Migration, upload and tratata folders will be created but there will be no images in the tratata folder.
- Fixed: Mapping for extranet groups in the MigrationConfig is incorrect in the migrationmodule.config file.
- Fixed: Open Sitecore 4. Edit the Text field of the Home node in the HTML Editor. Insert an image. Accept. Save. Migrate the Home node to Sitecore CMS 53 with the Merge option. All handlers are in gear. (and processMediaForFolders=|/upload/|" too). Remove the folder that was created in the Media Library for migration. Perform migration one more time. Image isn't inserted into the Text field of the Home node. The Migration folder is not created in the Media Library.
- Fixed: Create a user with the name Audrey in SC4. Start the transferring to SC53 process with the Overwrite option set on the Security database. Select Audrey for transferring. Set path = Security: sitecore/Users/Sample. After migration, there are two users with the name Audrey under the /sitecore/Users/Sample folder.
- Fixed: ImageFieldHandler has been added to the migration config file.
- New Feature: ImageFieldHandler has been added to the migration config file.
- New Feature: ContentMapping section has been added to the migration config file. Language mapping and field type mapping has been implemented in the ContentMapping functionality.
- New Feature: Name of the language item from the source solution is applied to the Display Name field. In such case there will be items with the same name in the source and target solutions.
Data Migration Service v.1.4.4 is released.
Sitecore versions: tested with Sitecore CMS v5.3.1 rev.070515.
- New Feature: It is possible to migrate media items which are stored as files from Sitecore CMS 5.3.1 to earlier versions of Sitecore.
April 11, 2007
Data Migration Wizard v1.4.3 is released.
Sitecore versions: tested with Sitecore CMS v5.3.1 rev. 070328.
- Fixed: After migration from 5.2, the media items have empty extension, height, width, etc. Fields.
- Fixed: The createMediaItems makes a lot of broken links if file is located at folder with spaces, for instance: /upload/my media items/site 1/product catalog.
- Fixed: Data Migration Wizard is unable to fetch images and files from the source installation if the source installation is using other port than 80.
- New Feature: MediaHandler was changed. Now we are able to copy media items during migration process.
Data Migration Service v1.4.3 is released.
Sitecore versions: tested with Sitecore CMS v5.3.1 rev. 070328.
February 15, 2007
Data Migration Wizard v1.1.3 is released.
Sitecore versions: tested with Sitecore CMS v5.1.1.22 and 5.2.0.13. Expected to work with Sitecore 5.1.1.x and 5.2.0.x.
List of Changes
Bug Fixes:
- When you migrate a large number of items and the migration manager divides the transfer throughout several requests, items which were postponed to transfer into a single request should be transferred directly after the main request. Now they are placed in the end of the transferred queue.
- Run the Migration Wizard and connect to the source site (4.x) with
- You can specify the transferring mapping for items in the MigrationConfig file. This mapping won't be used in the wizard tree (for example, you want to transfer items which do not exist in your target database. But you specified the mapping for this item to another item from your database. The item which you want to transfer will be marked as non-existant).
- Upload the png image to SC4 with the Media module installed. Transfer the image, jpeg, gif and file templates to SC5.1. Transfer the image to the media library of SC5.1. The Width/Height fields are empty, thus they are filled in SC4.
New features:
- A new processor has been added to the Migration configuration file to transfer media items with correct templates.
Data Migration Service v1.1.3 is released.
Sitecore versions: tested with Sitecore CMS v5.1.1.22 and 5.2.0.13. Expected to work with Sitecore 5.1.1.x and 5.2.0.x.
Data Migration Wizard v1.3.3 is released.
Sitecore versions: tested with Sitecore CMS v5.3.0 Build 061102. Expected to work with Sitecore 5.3.x.
List of Changes
Bug Fixes:
- When you migrate a large number of items and the migration manager divides the transfer throughout several requests, items which were postponed to transfer into a single request should be transferred directly after the main request. Now they are placed in the end of the transferred queue.
- Run the Migration Wizard and connect to the source site (4.x) with
- You can specify the transferring mapping for items in the MigrationConfig file. This mapping won't be used in the wizard tree (for example, you want to transfer items which do not exist in your target database. But you specified the mapping for this item to another item from your database. The item which you want to transfer will be marked as non-existant).
- In V4, the EMBED tag was used for creating links to SWF files in HTML fields. Such links are not updated after conversion.
New features:
- The 'parameters' attribute has been added to the Html field handler to handle links in the HTML field when the media item is absent.
Data Migration Service v1.3.3 is released.
Sitecore versions: tested with Sitecore CMS v5.3.0 RC3. Expected to work with Sitecore 5.3.x.
Data Migration Service v1.0.4 is released.
Sitecore versions: tested with Sitecore CMS v4.3.2.13. Expected to work with Sitecore 4.3.2.x.
List of Changes
Bug Fixes:
- There is no way to correctly transfer media items from Sitecore 4 with the Media module installed.
- Create a user in SC4 with the Blank Password checkbox checked and fill the Password field for the user. Migrate this user to SC51/52/53. Try to log in this user using empty password. It isn't possible but the user is logged in successfully to SC4 with empty password.
Workaround: Migrate the user with the empty password if the Blank Password checkbox is checked in SC4 and don't care about the value of the Password field.
New features:
- New option has been added to correctly transfer items with the Item Link filled.
- Option for transferring only latest versions of an item has been added.
January 11, 2007
Data Migration Service v1.0.3 is released.
Sitecore versions: tested with Sitecore CMS v4.3.2.13. Expected to work with Sitecore 4.3.2.x.
List of Changes
Bug Fixes:
- The created/updated dates are set to the wrong value after migration when they are empty in the source.
- Security Assignments for an item are wrong after server restart.
New features:
- New Option was added: now only the latest item versions can be transferred.
Data Migration Wizard v1.3.2 is released.
Sitecore versions: tested with Sitecore CMS v5.3.0 061220. Expected to work with Sitecore 5.3.
List of Changes
Bug Fixes:
- Items with the same name should be transferred correctly.
- The Html field doesn't convert to Rich Text.
- The updated date is set to wrong value after migration.
- Non-administrator users have rights for migration.
- The created/updated dates are set to the wrong value after migration when they are empty in the source.
- When the item path is too long, the entire area inside the wizard is moved.
- Proxy items lose the target source if transferred for the second time with merge.
New features:
- New Option was added to the service: now only the latest item version can be transferred.
- The log file now contains information about a failed attempt to change the image in the html field.
- Handlers can be excluded from the attribute with the 'off' option.
- Known media extensions are handled now.
Data Migration Wizard v1.1.2 is released.
Sitecore versions: tested with Sitecore CMS v5.1.1.22 and 5.2.0.13. Expected to work with Sitecore 5.1.1.7 and later and Sitecore 5.2.x.
List of Changes
Bug Fixes:
- Media Items from the Media Module are transferred incorrectly from Sitecore V4.
- Filters are not visible during migration from Service 5.1.
- File field type of the item from Sitecore 4.3.X is filled incorrectly after migration.
- When the item path is too long, the entire area inside the wizard is moved.
New features:
- The configuration section in web.config and a new column in the wizard’s second page were added.
- New Option was added to the service: only the latest item version can now be transferred.
- Wizard doesn’t connect to service after all configurations are done and before the first request for data migration is made.
- Transferring log (log in the wizard) is smaller now.
- Filled File field type is transferred correctly from Sitecore 4.3.X.
December 12, 2006
Data Migration Wizard v1.0.2 is released.
Sitecore versions: tested with Sitecore CMS v4.3.2.13. Expected to work with Sitecore 4.3.2.x.
List of Changes
Bug Fixes:
- Non-administrator users have rights for migration.
November 30, 2006
Data Migration Wizard v1.3.1 is released.
Sitecore versions: tested with Sitecore CMS v5.3.0 061102. Expected to work with Sitecore 5.3.0 and later.
List of Changes
Bug Fixes:
- Media items become media files in the target installation when proxies are transferred.
- Created date and Updated date are not transferred correctly.
New features:
- Media streams conversion improved;
- Wizard doesn’t connect to service after all configurations are done and before the first request for data migration is made
- The handler for converting of the Html fields to Rich Text fields is implemented
- Transferring log (log in the wizard) is smaller now.
- Filled File field type from Sitecore 4.3.X is transferred correctly
- The handlers which correct the references to the media items stored in the database in Html, Rich text, File and Image fields are improved.
November 10, 2006
Data Migration Wizard v1.3.0 is released.
Sitecore versions: tested with Sitecore CMS v5.3.0. Expected to work with Sitecore 5.3.0 and later.
List of Changes
New features:
- SOAP extension is enabled (the size of data to be transferred should be less compared to the previous versions of the module).
- Request timeout is added.
- Customization of the transferring process is implemented.
- Configuration file for the module is created.
September 28, 2006
Data Migration Wizard v 1.2.1 is released.
Sitecore versions: tested with Sitecore CMS v5.2.0.12. Expected to work with Sitecore 5.2.0.3 and later.
Data Migration module v 1.1.1 is released.
Sitecore versions: tested with Sitecore CMS v5.1.1.21. Expected to work with Sitecore 5.1.1.17 and later.
List of Changes (for versions 1.2.1 and 1.1.1).
Bugs fixed:
- Empty item versions aren’t migrated.
- Item name is truncated if it has more than 100 characters.
- Log4net configuration is changed.
- ClearChildren description expanded.
- Wrong item strip.
New features:
- Request Timeout setting is added.
- Error concerning the huge size is added to the main log only.
- SOAP extension is enabled.
Data Migration Wizard v 1.0.1 is released.
Sitecore versions: tested with Sitecore CMS v4.3.2.13. Expected to work with Sitecore 4.3.x releases.
List of Changes.
Bugs fixed:
- Custom items can't be migrated from Sitecore 4.
- Items with characters listed in InvalidItemNameChars can't be transferred.
- Icon field is filled with some value in the target database, while it should be empty.
- Versions problem after migration.
- Empty item versions aren't migrated.
New features:
- Two transferring options are added (Icon and Editor fields can be trasferred)
- 'Inherit Security' field is added when migrating from Sitecore V4.
July 11, 2006
Data Migration Wizard v 1.2.0 is released.
Sitecore versions: tested with Sitecore CMS v5.2.0.x and 5.1.1.x.
Changes:
- Fixed: Issue with logging assembly. New application setting is added to specify the logging assembly.
April 10, 2006
Data Migration Wizard for Sitecore 5.2 is released./p>
Sitecore versions: tested with Sitecore CMS v5.2.0.3.
April 04, 2006
Data Migration Wizard is released.
Sitecore versions: tested with Sitecore CMS v5.1.1.11. Expected to work with 5.1.1.x releases.
2. Known Issues
The list of known issues sfor the current version(s) of the package
Data Migration Module for Sitecore 5.3
- Fields’ values that refer to virtual items will be broken since virtual items receive different IDs on the target than on the source installation.
Workaround: Move all records from the Shadows table manually to fix this problem. - The section:
<webServices>
<soapExtensionTypes>
<add type="TransferProtocol.SoapExtensions.SoapArchiveExtension,TransferProtocol"
priority="1"
group="0" />
</soapExtensionTypes>
</webServices>in the configuration file may prevent other web services from normal work. You should comment this section if you don’t need the Migration Module at that moment.
- Repeated transfer of proxy items under the Home node multiples the Home node if the target has activated proxy items.
- Specify /sitecore/layout/layouts in the Item Link field of the Home node (SC4). Migrate Layouts to SC53. Migrate the Home node to SC53 with the Process Item Links option. Migrate the Home node to SC53 with the Process Item Links option for the second time. Two identical proxy items were created.
- Problem with FileFieldHandler: If the FileFieldHandler cannot retrieve a media item by its path in the file field, such media item will not be transferred to the target installation. Such problems occur only when transferring from Sitecore CMS version 5.1 or 5.2.
- A media item will be created in the “Migration folder” if such option is specified: processMediaForFolders=|/~/media/| but the fields of the item (Extension, etc.) will not be filled properly. A special handler for such items should be written.
- An exception may occur when a user clicks the Next button on the General Options page.
This can be caused by the incorrectly created backup XML files. The problem can be fixed by deleting the folder with XML files. This folder is specified in the following item: /sitecore/system/modules/migration/settings. - Memo fields with value “ ” are being assumed to be empty.
- Workflow history can’t be transferred by the Migration tool
Data Migration Service for Sitecore 4.3.2.X
- If a sublayout is tied to a layout, while an XSL rendering is tied to this sublayout, Sitecore V4 ties renderings and sublayouts in incorrect rendering order.